Chapter 23. Using Third-Party Management Utilities

Table of Contents
23.1. Third-Party Management Concepts
23.2. Third-Party Management Tasks

This chapter discusses the use of third-party utilities to manage the SpinServer. The SpinServer supports Simple Network Management Protocol (SNMP) for discovery and delivery of critical events via SNMP traps. The SpinServer supports SNMPv1 (version 1) and SNMPv2c (version 2).


23.1. Third-Party Management Concepts

SNMP is a client/server protocol in which an agent, or server, runs on the device being managed (in this case, the SpinServer). The agent relays the status of the device to a managing entity, or client, which runs on a separate machine. The SpinServer communicates with SNMP-based management utilities by using SNMP trap destinations, which notify the management utility when specific events occur on the SpinServer.

To use SNMP-based third-party utilities with the SpinServer system, you must first set up SNMP trap destinations. You can then use a Network Management Station (NMS) or other device capable of receiving SNMP traps with the SpinServer system. The NMS or other device is referred to as a trap destination.


23.2. Third-Party Management Tasks

To use an SNMP-based management utility, you must set up SNMP trap destinations.

23.2.1. Setting Up SNMP Trap Destinations

Use the services snmp trapdest commands to set up SNMP trap destinations.

23.2.1.1. Creating an SNMP Trap Destination

Use the services snmp trapdest new command to create an SNMP trap destination. The syntax of the command follows:

services snmp trapdest new -ipaddress IP_address -trapport trap_port -community community -snmpversion {SNMPv1 | SNMPv2c}

The following example creates an SNMP trap destination on a Network Management Station (NMS) at IP address 10.127.5.10 that uses port 162 to receive SNMP traps. The trap destination belongs to a community named public and uses SNMPv2c.

spinserver::> services snmp trapdest new -ipaddress 10.127.5.10 -trapport 162 -community public -snmpversion SNMPv2c

23.2.1.2. Displaying Information about an SNMP Trap Destination

Use the services snmp trapdest show command to display information about one or more SNMP trap destinations. Use the command with the -ipaddress parameter to display information about a specific trap destination, or without the parameter to display information about all trap destinations. The command has the following syntax:

services snmp trapdest show [-ipaddress IP_address]

The following example displays information about all SNMP trap destinations:

spinserver::> services snmp trapdest show
IP Address  Trap Port  Community  SNMP Version
10.10.127.1  162        public     SNMPv2c
10.10.127.2  162        public     SNMPv1

23.2.1.3. Modifying an SNMP Trap Destination

Use the services snmp trapdest modify command to modify an SNMP trap destination. The syntax of the command follows:

services snmp trapdest modify -ipaddress IP_address -trapport trap_port -community community -snmpversion {SNMPv1 | SNMPv2c}

The following example modifies an SNMP trap destination on a Network Management Station (NMS) at IP address 10.127.5.10 that uses port 162 to receive SNMP traps. The trap destination belongs to a community named public and uses SNMPv1.

spinserver::> services snmp trapdest modify -ipaddress 10.127.5.10 -trapport 162 -community public -snmpversion SNMPv1

23.2.1.4. Deleting an SNMP Trap Destination

Use the services snmp trapdest delete command to delete an SNMP trap destination. The command has the following syntax:

services snmp trapdest delete -ipaddress IP_address

The following example deletes an SNMP trap destination at IP address 10.127.5.10:

spinserver::> services snmp trapdest delete -ipaddress 10.127.5.10

Copyright © 2004 Network Appliance, Inc.; copyright © 2003, 2004 Spinnaker Networks, LLC. All rights reserved. Specifications subject to change without notice.